0.0
NA
CVE-2026-31241
Apache Mem0 Unauthenticated Memory Deletion Vulnerability
Description

The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.

INFO

Published Date :

May 12, 2026, 6:16 p.m.

Last Modified :

May 12, 2026, 6:16 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-31241 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Implement authentication and authorization for the memory deletion API endpoint.
  • Enforce authentication on the DELETE /memories endpoint.
  • Validate user authorization before deleting memory records.
  • Restrict access to authorized personnel only.
  • Log all memory deletion attempts.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-31241.

URL Resource
https://github.com/mem0ai/mem0
https://www.notion.so/CVE-2026-31241-35d1e139318881459ae5e6f0d7dc6f0f
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-31241 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-31241 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-31241 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-31241 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    May. 12, 2026

    Action Type Old Value New Value
    Added Description The mem0 1.0.0 server lacks authentication and authorization controls for its memory deletion API endpoint (DELETE /memories). The endpoint allows unauthenticated users to delete memory records by specifying arbitrary user identifiers (e.g., user_id, run_id, agent_id) in the request query parameters. A remote attacker can exploit this by sending unauthenticated DELETE requests to erase memory data for any user, leading to unauthorized data loss and denial of service.
    Added Reference https://github.com/mem0ai/mem0
    Added Reference https://www.notion.so/CVE-2026-31241-35d1e139318881459ae5e6f0d7dc6f0f
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.